“^1” and “^0” are incompatible fields. Only one of them is a container field. Proceed anyway?
This relationship will not work because the field “^1” is a container field. Proceed anyway?
Checking for unique or existing values will not work because the field “^1” cannot be indexed. Proceed anyway?
“^0”, which is a match field in this relationship, is also the destination of a lookup. This circular definition is not allowed.
This relationship will not work because the field “^1” cannot be indexed. Proceed anyway?
The calculation “^1” cannot be stored or indexed because it references a related field, a Global field, a Summary field or an unstored Calculation in its formula.
The field type of “^0” cannot be changed because “^0” is used by the relationship “^1”.
Permanently deleting “^1” will invalidate all references to it. Proceed anyway?
Value list names must be between 1 and 60 characters and must be unique. Please type a valid name before clicking the create button.
Relationship names must be between 1 and 60 characters and may not contain a “:”. Please type in a valid relationship name.
The relationship name “^1” is not unique.
The summarised field must be a Text, Number, Date, Time, Global or Calculation field.
When changing to or from a Global field, all data in the field will be lost. Proceed anyway?
The field “^0” has been defined to have more repetitions than the field “^1” in this file. As a result, some data may not be copied when a lookup is performed. Proceed anyway?
When changing to or from a Container field, all data in the field will be lost. Proceed anyway?
When changing the field type to Calculation or Summary, FileMaker will replace any data in the field with the result of the formula. Proceed anyway?
When changing the field type from Text to Number, Date, or Time, FileMaker will put the data on one line. Any data after the first 255 characters will be permanently deleted. Proceed anyway?
This name cannot be used in a calculation formula because it